NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: SBACKUP files DOCUMENT ID: TID014522 DOCUMENT REVISION: A DATE: 14JAN94 ALERT STATUS: Yellow INFORMATION TYPE: Symptom Solution README FOR: SBACK2.EXE NOVELL PRODUCT and VERSION: NetWare 3.12 NetWare 4.01 ABSTRACT: SBACKUP files for NetWare 3.12 and NetWare 4.0x. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 SYMPTOM General enhancements needed SOLUTION Apply SBACK2.EXE Self-Extracting File Name: SBACK2.EXE Revision: A Files Included Size Date Time \ SBACK2.TXT (This File) SMDR.NLM 41362 10-28-93 5:11p SBACK2.DOC 6612 01-14-94 2:46p WS_MAN.NLM 35146 12-16-93 10:51a TSA_DOS.NLM 77820 11-08-93 8:46a TSA_OS2.NLM 7814 11-02-93 5:20p TSA_SMS.COM 17724 10-18-93 4:37p (DOS version only) \3.12\ TSA311.NLM 129464 11-05-93 2:36p TSA312.NLM 129461 11-05-93 2:28p SMDR31X.NLM 41649 10-28-93 5:14p \4.0X\ TSA400.NLM 122492 11-05-93 2:20p SBACKUP.NLM 234976 08-17-93 1:56p Installation Instructions: Installation instructions for 4.0x and 3.12 1. Flag all SBACKUP files SRW in SYS:SYSTEM for the version of Netware being updated (See list above). Note: The TSA_SMS.COM for DOS resides in the SYS:PUBLIC subdirectory. 2. Rename the SBACKUP files to *.old. 3. Copy all update files, for the version of Netware being updated, to the SYS:SYSTEM directory. 4. Flag the files back to ROS. ********************** * A WORD OF CAUTION: * ********************** At the present time SBackup does NO READ-AFTER-WRITE verification of the data that is backed up. Therefore it is important that you verify your backups manually. One way of accomplishing this is to follow example 1 in the Commonly Asked Questions section -- "How to Restore a file to a new location." Restoring several files to a new location and doing a DOS compare on the restored files with their originals will verify that files are being backed up correctly and that they can be restored. It should be kept in mind that this in no way represents a complete verification. It is recommended that you do this with every backup set that you make and should be made a regular step in your backup procedures. Solution Specifics: Explanation of TAPEDAI.DSK and DIBIDAI.NLM: TAPEDAI.DSK TAPEDAI.DSK is a NetWare 386 device driver written to control certain tape devices. It is used with DIBIDAI.NLM. DIBIDAI.NLM presents a DIBI interface to SBACKUP.NLM, but translates the DIBI requests into NetWare DAI calls. This eventually results in device driver calls getting passed to TAPEDAI.DSK through the same IO request mechanism used by NetWare to obtain disk service. TAPEDAI.DSK must be loaded prior to loading SBACKUP. If it is used often, the user may want to load it from within the STARTUP.NCF file. With Netware v4.0x and v3.12 if TAPEDAI.DSK is loaded anywhere other than the STARTUP.NCF file (i.e. Server console prompt or the AUTOEXEC.NCF) the command "SCAN FOR NEW DEVICES" will need to be performed after TAPEDAI.DSK is loaded and before Sbackup is loaded or the tape drive will will not be seen. Dependencies: TAPEDAI.DSK targets any ASPI compliant disk drivers. Check with the driver manufacturer to confirm ASPI compliancy. Consequently, the ASPI compliant disk driver must be loaded prior to loading TAPEDAI.DSK. Target Devices: TAPEDAI has been tested (not necessarily certified) with the following devices: Manufacturer Product ARCHIVE Python CIPHER T826 (half inch - 2.6 Gig) CIPHER T860 (half inch - 6 Gig) EXABYTE EXB-8500 HP HP35450A HP HP35470A* HP HP35480A* TANDBERG TDC 3800 TANDBERG TDC 4100 TANDBERG TDC 4200 WANGDAT 1300 WANGDAT 3200 WANGTEK 5525ES WANGTEK 6130 WANGTEK WANGTEK_6130_HS A GENERIC driver has been added to TAPEDAI.DSK which will support most SCSI interface tape drives (the ONLY Exabyte that will work with TAPEDAI.DSK is the EXB-8500 -- all others will not be seen). Novell makes no guarantee as to the correct functionality of any drive not listed above. The customer assumes all responsibility for testing their tape drive solution with sbackup to insure correct functionality. * (The HP35470A and HP35480A must be set through its dip switches so that the SCSI Valid Bit is set upon crossing Early Warning. If this is not done, sessions that span tapes won't be reliable. Users should perform a test backup and restore across tapes to confirm that the switches are set properly. The file that actually spans tapes is the one to test.) SMDR.NLM Storage Management Data Requester. Controls transfer of data and commands between Sbackup engine and the TSA. TSA Files TSA311.NLM Target Service Agent for v3.11 server. Loads in conjunction with SMDR31x.NLM. Allows a v3.11 server to be backed up or restored from a v3.12 or 4.0x server. TSA312.NLM Target Service Agent for v3.12 server. SMDR31x.NLM Support module for v3.1x service agents. TSA400.NLM Target Service Agent for v4.0x server. TSA_DOS.NLM Target Service Agent for DOS clients. Used in conjunction with TSA_SMS.COM. WS_MAN.NLM Support module for TSA_DOS.NLM. TSA_OS2.NLM Target Service Agent for OS/2 clients. Used in conjunction with TSA_SMS.COM for OS/2. �